home *** CD-ROM | disk | FTP | other *** search
/ IRIX Base Documentation 2001 May / SGI IRIX Base Documentation 2001 May.iso / usr / share / catman / p_man / cat3dm / audiofile / AFgetmarkname.z / AFgetmarkname
Encoding:
Text File  |  1998-10-20  |  4.2 KB  |  67 lines

  1.  
  2.  
  3.  
  4. aaaaffffGGGGeeeettttMMMMaaaarrrrkkkkNNNNaaaammmmeeee((((3333ddddmmmm))))                                          aaaaffffGGGGeeeettttMMMMaaaarrrrkkkkNNNNaaaammmmeeee((((3333ddddmmmm))))
  5.  
  6.  
  7.  
  8. NNNNAAAAMMMMEEEE
  9.      afGetMarkName, afGetMarkComment - get the name or comment string for a
  10.      given marker id in an audio track
  11.  
  12. SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
  13.      ####iiiinnnncccclllluuuuddddeeee <<<<ddddmmmmeeeeddddiiiiaaaa////aaaauuuuddddiiiiooooffffiiiilllleeee....hhhh>>>>
  14.  
  15.      cccchhhhaaaarrrr ****aaaaffffGGGGeeeettttMMMMaaaarrrrkkkkNNNNaaaammmmeeee((((AAAAFFFFffffiiiilllleeeehhhhaaaannnnddddlllleeee ffffiiiilllleeee,,,, iiiinnnntttt ttttrrrraaaacccckkkkiiiidddd,,,, iiiinnnntttt mmmmaaaarrrrkkkkiiiidddd))))
  16.  
  17.      cccchhhhaaaarrrr ****aaaaffffGGGGeeeettttMMMMaaaarrrrkkkkCCCCoooommmmmmmmeeeennnntttt((((AAAAFFFFffffiiiilllleeeehhhhaaaannnnddddlllleeee ffffiiiilllleeee,,,, iiiinnnntttt ttttrrrraaaacccckkkkiiiidddd,,,, iiiinnnntttt mmmmaaaarrrrkkkkiiiidddd))))
  18.  
  19. PPPPAAAARRRRAAAAMMMMEEEETTTTEEEERRRR
  20.      _f_i_l_e     is an AAAAFFFFffffiiiilllleeeehhhhaaaannnnddddlllleeee structure, previously created by a call to
  21.               aaaaffffOOOOppppeeeennnnFFFFiiiilllleeee(3dm).
  22.  
  23.      _t_r_a_c_k_i_d  is a positive integer value which identifies an audio track in
  24.               _f_i_l_e.  All currently supported file formats allow exactly one
  25.               audio track per file, so the value AAAAFFFF____DDDDEEEEFFFFAAAAUUUULLLLTTTT____TTTTRRRRAAAACCCCKKKK should
  26.               always be used here for now.
  27.  
  28.      _m_a_r_k_i_d   is a positive integer value which identifies a marker structure
  29.               in the audio track given by _t_r_a_c_k_i_d.  You obtain marker ID's by
  30.               calling aaaaffffGGGGeeeettttMMMMaaaarrrrkkkkIIIIDDDDssss(3dm).  You can call aaaaffffIIIInnnniiiittttMMMMaaaarrrrkkkkIIIIDDDDssss(3dm) to
  31.               assign your own ID's when you create a new audio file.
  32.  
  33. RRRREEEETTTTUUUURRRRNNNN VVVVAAAALLLLUUUUEEEE
  34.      aaaaffffGGGGeeeettttMMMMaaaarrrrkkkkNNNNaaaammmmeeee(((()))) returns a null-terminated string containing the name
  35.      associated with the specified marker, or the null string on error.
  36.      aaaaffffGGGGeeeettttMMMMaaaarrrrkkkkCCCCoooommmmmmmmeeeennnntttt(((()))) returns a null-terminated string containing the
  37.      comment associated with the specified marker, or the null string on
  38.      error.
  39.  
  40. DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
  41.      The AIFF-C (AIFF) spec includes locations for name strings in marker
  42.      structures.  For example, the marker which holds the beginning sample
  43.      frame location for the sustain loop might be named "begin sustain loop".
  44.  
  45.      The WAVE (RIFF) format spec includes "cues" and associated data
  46.      describing each "cue".  In addition to the position and name string, a
  47.      "note" is included in this data.  The AF maps the mark position, name and
  48.      comment into these portions of the description.
  49.  
  50.      See wwwwaaaavvvveeee(4) for more details about cues.
  51.  
  52.      See the AIFF-C spec and aaaaiiiiffffffff(4) for more details about markers.
  53.  
  54. SSSSEEEEEEEE AAAALLLLSSSSOOOO
  55.      afOpenFile(3dm), afGetMarkIDs(3dm), afInitMarkIDs(3dm),
  56.      afInitMarkName(3dm), afInitMarkComment(3dm)
  57.  
  58.  
  59.  
  60.  
  61.  
  62.  
  63.                                                                         PPPPaaaaggggeeee 1111
  64.  
  65.  
  66.  
  67.